Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I wanted to use flyway 2.1.1 because newer versions can fetch SQL migrations from anywhere of the filesystem. (locations=filesystem:somedir)
I did a few simple tests (clean, init, migrate and status) and they all seem to work fine with a simple SQL migration. I have not tested any Java migrations though.
There are probably some problems with existing migrations (see http://flywaydb.org/documentation/releaseNotes.html) when upgrading to 2.1.1
The most problematic in my case is that initVersion is not set to 0 anymore but it is 1 instead. This means 'gradle flywayInit' will create version 1 and if you call your own migration also 1, your migration is not run. So you should not create migrations with version 1.
Thanks.